UFAL/Use gh cli dispatch for rest tests#1252
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the deploy workflow to trigger and monitor REST test runs via GitHub CLI workflow dispatch, enabling REST tests to be executed with customer-specific inputs after deploy/import flows.
Changes:
- Replaces
curl-based workflow dispatch + manual polling withgh workflow run+gh run watch. - Passes
CUSTOMERandURLinputs to thedataquest-dev/dspace-rest-testworkflow dispatch. - Skips
rest-tests-after-deploy8whenIMPORTis enabled (aligning execution with the deploy path).
vidiecan
requested changes
Mar 17, 2026
vidiecan
approved these changes
Mar 18, 2026
This was referenced Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem description
We updated rest tests in order to run tests according to specific customers and we have to change the way how it is called from deploy workflow.
Related issues:
https://github.com/dataquest-dev/dspace-customers/issues/467
https://github.com/dataquest-dev/dspace-customers/issues/468
Sync verification
If en.json5 or cs.json5 translation files were updated:
yarn run sync-i18n -t src/assets/i18n/cs.json5 -ito synchronize messages, and changes are included in this PR.Manual Testing (if applicable)
Copilot review